Hi Tom,
Apparently the Start button is using
Debounce, but not the Estop. I didn't know the Debounce
would help with the noise, so I will change that see if
it makes the issue stop.
What are your thoughts on changing
from disabling the axis to simply stopping motion using
Jog(0,0),etc.? Could the user then simply press the
Start button to continue if it was determined the stop
wasn't necessary?
Thanks for your guidance,
David.
On 12/4/2016 4:35 PM, Tom
Kerekes
tk@...
[DynoMotion] wrote:
Hi David,
That would make sense.
Are you using the Debounce
function to observe the input? That would tend to
filter noise.
The PC_COMM_ESTOP sends a
command to KMotionCNC to push the Stop Button. Your
current method should be more reliable as it doesn't
depend on the PC.
Regards
TK
Hi Tom,
It looks like the print
out is from the program which monitors
external buttons. The machine has a pendant
with a Start and Estop button which are setup
to trigger bits. The Estop function is written
to disable all axis. I think there may be a
noise issue triggering this as the problem is
random.
Just out of curiosity,
what exactly does the DoPC(PC_COMM_ESTOP)
function do? I'm not using it, as my program
was written to disable the individual axis,
but it may be a better option for this
problem.
Thanks for your help,
David.
On 12/3/2016 1:43 PM,
Tom Kerekes
tk@...
[DynoMotion] wrote:
Hi David,
For us to help
you would need to provide more information.
What is the history? Did this ever work?
What changes were made? Is it a consistent
failure? Are the axes actually disabled?
Can you re-enable them? Have you tried
other commands/GCode? Lower Speeds?
I believe that
print out is in the code. You might find an
editor that can do a "find in files" for use
when you can't find something. Visual Studio
has a great one.
Regards
TK
|
This email has been checked for viruses by Avast
antivirus software.
www.avast.com
|